Methods, systems, and products for categorizing and converting attached objects

ABSTRACT

Methods, systems, and products systems are disclosed for categorizing and converting an attached object. An electronic message is received from a sender&#39;s address that is destined for a recipient&#39;s address and has the attached object associated with a sender legacy system. The sender&#39;s address and the recipient&#39;s address are associated to a list of addresses. When both the sender&#39;s address and the recipient&#39;s address are matched to the list of addresses, then the electronic message is sent to a rule-based engine that interprets the attached object using a set of rules and that categorizes the attached object. The object is converted based on the category. When the sender&#39;s address and the recipient&#39;s address do not match the list of addresses, then an identifier is received that associates the electronic message with another system.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.10/253,470, filed Sep. 24, 2002 and now issued as U.S. Pat. No.7,376,704, which is incorporated herein by reference in its entirety.This application also relates to application Ser. No. 10/253,500,entitled “Network-Based Healthcare Information Systems”, filed Sep. 24,2002 and now issued as U.S. Pat. No. 7,298,836, which is alsoincorporated herein by reference in its entirety.

NOTICE OF COPYRIGHT PROTECTION

A portion of the disclosure of this patent document and its figurescontain material subject to copyright protection. The copyright ownerhas no objection to the facsimile reproduction by anyone of the patentdocument or the patent disclosure, but the copyright owner otherwisereserves all copyrights whatsoever.

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention generally relates to computer networks and to telephony.More particularly, this invention is directed to methods and systems formore efficient and effective communication and processing of electronicdata in a telecommunications network-based information system.

2. Description of the Related Art

In Epidemics, Hippocrates wrote “[t]he art of medicine has threefactors: the disease, the patient and the physician.” Were he writingtoday, the Father of Medicine would also likely include “access toinformation” as a fourth factor. Why? Because today's marketplace isdriven by increasing pressure for cost controls, by the increasedstrength, of the consumer voice, by a shift from hospital inpatient caretowards primary, ambulatory, and home care, by an emphasis on “casemanagement,” by increased competition, and by the focus on quality thatis necessary for better patient care. This relentless drive to improveefficiencies and cut costs makes many traditional proceduresinefficient. This relentless drive also presents great opportunities forhealthcare professionals, organizations, and patients to enter into newtypes of multi-institution partnerships (e.g., strategic alliancesbetween physician's offices, hospitals, clinics, labs, diagnosticcenters, medical record repositories, insurers, patients, pharmaceuticaland surgical suppliers, other vendors, etc.) that utilize many differentcomputing systems and other communications technologies to manage andshare electronic healthcare information. One of the biggest harriersfacing these multi-institution partnerships is creating and maintainingan integrated delivery system (IDS) that facilitates aninformation-exchange of standardized or otherwise compatible data sothat each participant in the partnership has efficient and effectiveaccess to the information.

Thousands, if not hundreds of thousands or more, of electronicdocuments, emails, and proprietary information are generated each dayand shared among these multi-institution partnerships. For example, aphysician might order a complex lab test from the local hospital.Instead of waiting on the results to arrive by hand delivery, thephysician's office may get online and requests it via secure, encryptedemail. The hospital's lab staff either manually attaches the lab resultto a return email, or, in more advanced systems, the lab system respondsautomatically to the request and returns the results to a legacy systemaccessible by the physician. Another example is when a physician needsto admit a patient to the hospital. Instead of having the staff call theadmission office and spend upwards of thirty (30) minutes talking andwaiting on hold, the office sends the pre-admission informationelectronically, including patient record information and pre-admissionorders to the hospital via an email attachment or directly to thehospital's legacy system. As used herein, the term “legacy systems”includes data processing, storage, management, and information systems,such as, for example, electronic patient health history, patientinsurance information, demographic information, and physical records.Typically, the legacy systems are customized in terms of software,hardware, and network configuration for each participant of themulti-institution partnership. Typically, the legacy system includes anetwork of multiple computer systems; however, the legacy system mayalso be a stand-alone computer system.

In both of the above examples, the shared healthcare information may beprocessed in a variety of ways. For example, the hospital may provideinformation to the physician by transmitting healthcare data over aLocal Area Network (LAN) connection into a database on a web server.This healthcare information could then be transmitted to the physician'scomputer system over a data connection, such as the Internet, Intranetor Extranet, or over a direct connection, such as dial up access, usingpush technology that automatically broadcasts the data to thephysician's computer system and allows the physician to view thetransmitted healthcare data using an appropriate software package, suchas a browser. While the goal of the IDS interface of aninformation-exchange system is to translate and reformat the healthcareinformation from one legacy system so that it is compatible with anotherlegacy system(s), thus far, the IDS systems have been primarily limitedto very specialized healthcare information and limited in the featuresand services offered between linked legacy systems.

In addition to the challenges of implementing a successful IDS thatenables the exchange of electronic healthcare information, most of theparticipants in the multi-institution partnerships must also comply witha variety of federal, state, local and other rules that protect theprivacy and security of healthcare information associated with apatient. For example, the Health Insurance Portability andAccountability Act (HIPAA), signed into law by President Clinton on Aug.21, 1996 (Pub. L. 104-191, 110 Stat. 1936), covers health plans,healthcare clearinghouses, and healthcare providers who conduct certainfinancial and administrative transactions (e.g., electronic billing andfunds transfers) electronically. Providers (e.g., physicians, hospitals,etc.) and health plans are required to give patients a clear writtenexplanation of how a covered entity may use and disclose a patient'shealthcare information. Further, healthcare providers are required toobtain patient consent before sharing information for treatment,payment, and healthcare operations. In addition, HIPPA also requiresthat a provider adopt and implement privacy procedures to ensure theprivacy and security of the healthcare information.

The above discussion illustrates how the sharing of healthcareinformation and technology are creating a new foundation for a virtualhealthcare setting. With this emerging virtual healthcare setting, whatare needed are improved network-based information systems that buildcommunications infrastructures to support different organizational needsand capitalize on emerging trends in the healthcare setting.Accordingly, network-based information systems and components are neededthat enable multiple legacy systems to share, transfer, and/or accessstandardized or otherwise compatible data of the various participants inthe multi-institution partnership. Further, a need exists to improvenotification, access, and management of the electronically sharedhealthcare information without investing millions of dollars in computerequipment, in a networking infrastructure, in maintenance, and intraining while also complying with security, authenticity, and/orprivacy requirements.

BRIEF SUMMARY OF THE INVENTION

The aforementioned problems and others are reduced by atelecommunications network-based information system (NBIS). The NBIScomprises systems and methods that leverage the assets of atelecommunications network to facilitate improved access, sharing,notification, security, and/or management of electronic data exchangedbetween or among different legacy systems. Some advantages of NBISinclude increased ability of each participant to flexibly manage andcategorize electronic data that is exchanged with other participants,provide faster access to electronic data, and utilize a localproprietary network to reduce or prevent, electronic data from enteringtraffic in a public data network, such as the Internet.

An embodiment of this invention describes a method that includesreceiving electronic data associated with a sender's legacy system,interpreting tire electronic data according to a rule-based engine tocategorize the electronic data, and processing the electronic data intoa receiver's legacy system. The sender's legacy system and thereceiver's legacy system are associated with an integrated deliverysystem that enables an exchange of selected electronic data between oneor more networks of communications devices associated with, atelecommunications service provider. In a preferred embodiment, arule-based application dataserver is used to categorize the electronicdata. The rule-based application dataserver allows a customer (e.g., aparticipant) to control access, sharing, notification, security, and/ormanagement of electronic data exchanged between or among differentlegacy systems. Typically, the rule-based application dataserver isassociated with a central office (“CO”), a mobile telephone switchingcenter (“MTSO”), or a combination CO/MTSO.

Another embodiment describes a method for communicating electronic datato a rule-based application dataserver associated with atelecommunications facility and allowing a customer (e.g., aparticipant) to manage the rule-based application dataserver includingone or more databases associated with a rule-based profile. Similar tothe first embodiment described above, the sender's legacy system and thereceiver's legacy system are associated with an integrated deliverysystem that enables an exchange of selected electronic data between oneor more networks of communications devices associated with atelecommunications service provider.

Another embodiment describes a method for establishing a data connectionbetween a sender legacy system and a receiver legacy system that uses arule-based application dataserver, communicating electronic data via thedata connection, and allowing a customer to manage the rule-basedapplication dataserver including one or more databases associated with arule-based profile. The rule-based application dataserver is provided bya telecommunications provider and controls access between the senderlegacy system and the receiver legacy system. Typically, the electronicdata includes an electronic message having an attached object, atransaction reply, a transaction notification, a compatible object,and/or other electronic communications.

Another embodiment describes a system for remotely managing electronicdata shared between different legacy systems communicating via atelecommunications connection that uses a rule-based applicationdataserver associated with a telecommunications facility. The systemincludes a network of interconnected communications devices serviced bya telecommunications service provider and a rule-based applicationdataserver for managing the exchange of electronic data betweendifferent legacy systems connected with the communications devices. Thesystem further includes an application program, referred to herein as aNBIS Management Module, that is installed in a customer's communicationsdevice, such as a computer system. The NBIS Management Module providesan interlace for the customer to remotely manage NBIS ManagementServices including the rule-based application dataserver and itsdatabases.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The above and other embodiments, objects, uses, advantages, and novelfeatures of this invention are more clearly understood by reference tothe following description taken in connection with the accompanyingfigures, wherein:

FIG. 1 is a block diagram showing of a NBIS Management Module thatresides in a computer system according to an embodiment of thisinvention;

FIG. 2 is a schematic showing an exemplary operating environment for atelecommunications network-based healthcare information system accordingto an embodiment of this invention;

FIG. 3 is a more detailed schematic of a rule-based applicationdataserver shown in FIG. 2;

FIG. 4 is a more detailed schematic of a hospital's legacy system shownin FIG. 2;

FIG. 5 is a schematic showing an exemplary framework for the flow ofelectronic message through the telecommunications network-basedinformation system according to an embodiment of this invention;

FIG. 6 is a schematic showing an exemplary operating environment for atelecommunications network-based real estate information systemaccording to an embodiment of this invention;

FIG. 7 is a schematic showing an exemplary embodiment of communicatingan electronic message using wired and wireless communications devicesassociated with the telecommunications network-based information systemaccording to an embodiment of this invention;

FIG. 8 is a schematic showing another exemplary embodiment ofcommunicating an electronic message using wired and wirelesscommunications devices associated with the telecommunicationsnetwork-based information system according to an embodiment of thisinvention; and

FIGS. 9-10 are flowcharts showing a method of providing thetelecommunications network-based information system service to acustomer according to an embodiment of this invention.

DETAILED DESCRIPTION OF THE INVENTION

This invention now will be described more fully hereinafter withreference to the accompanying drawings, in which exemplary embodimentsare shown. This invention may, however, be embodied in many differentforms and should not be construed as limited to the embodiments setforth herein; rather, these embodiments are provided so that thisdisclosure will be thorough and complete, and will fully convey thescope of the invention to those of ordinary skill in the art. Moreover,all statements herein reciting embodiments of the invention, as well asspecific examples thereof, are intended to encompass both structural andfunctional equivalents thereof. Additionally, it is intended that suchequivalents include both currently known equivalents as well asequivalents developed in the future (i.e., any elements developed thatperform the same function, regardless of structure).

Thus, for example, it will be appreciated by those of ordinary skill inthe art that the diagrams, schematics, flowcharts, and the likerepresent conceptual views or processes illustrating systems and methodsembodying this invention. The functions of the various elements shown inthe figures may be provided through the use of dedicated hardware aswell as hardware capable of executing associated software. Similarly,any switches shown in the figures are conceptual only. Their functionmay be carried out through the operation of program logic, throughdedicated logic, through the interaction of program, control anddedicated logic, or even manually, the particular technique beingselectable by the entity implementing this invention. Those of ordinaryskill in the art further understand that the exemplary hardware,software, processes, methods, and/or operating systems described herein,are for illustrative purposes and, thus, are not intended to be limitedto any particular named manufacturer.

A telecommunications network-based information system (NBIS) istypically a subject-specific group of related client, vendor, andservice-oriented participants that leverage the assets of atelecommunications network. The purpose of NBIS is to efficiently shareinformation, automate business processes, and enhance market position ofthe participants. In the case of a healthcare NBIS, participants mayinclude a local hospital, insurance companies, HMOs, affiliatedhospitals, clinics, physicians' offices, medical schools, universities,and strategic partners. Patients, as well as vendors, could also beincluded, as could service providers, such as clinical laboratories,pharmacy services, temporary agencies, private ambulance services, andsubspecialty services. After all, rapid communication and exchange ofinformation between these participants can make a critical difference inthe quality of patient care. Alternatively, as is apparent to those ofordinary skill in the art, other subject specific groups of relatedclient, vendor, and service-oriented participants may leverage theassets of a telecommunications network to provide an NBIS customized fortheir needs.

In most cases, each participant usually has its own legacy systems,including software, hardware, equipment, networks, and/or otherinformation technology assets. For example, a hospital commonly has alocal and/or a wide area network that utilizes Ethernet, dedicatedprivate lines. Frame Relay, ISDN, ATM, ADSL, and the like. Further,these legacy systems provide an interface to a data network, such as theInternet, Intranet, and/or Extranet, that may be locally or remotelyaccessed by a participant's user (e.g., a hospital employee using acomputer system within the hospital's legacy system).

This invention provides improved access, sharing, notification, routing,security, and/or management of electronic data exchanged between oramong different legacy systems. These legacy systems are associated witha rule-based application dataserver provided by a telecommunicationsservice provider. These legacy systems are also associated with anintegrated delivery system (IDS) that uses associated rules, fields,and/or files to process exchanged information into a selected legacysystem. As used herein, the term “electronic data” includes electronicmessages such as email, attached objects (e.g., an attached file to theemail), and compatible objects (e.g., an attached object that has beenprocessed by the rule-based application dataserver and the IDS to formatand/or standardize electronic information shared between a first and asecond legacy system). The term “electronic data” also includestransaction notifications and/or transaction replies generated by therule-based application dataserver and/or the IDS, and/or other means ofcommunicating electronic information between or among NBIS participants.

Referring now to the figures, FIG. 1 is a block diagram showing a NBISManagement Module 110 residing in a computer system 100. The NBISManagement Module 110 operates within a system memory device. The NBISManagement Module 110, for example, is shown residing in a memorysubsystem 112. The NBIS Management Module 110, however, could alsoreside in flash memory 114 or peripheral storage device 116. Thecomputer system 100 also has one or more central processors 120executing an operating system. The operating system, as is well known,has a set of instructions that control the internal functions of thecomputer system 100. A system bus 122 communicates signals, such as datasignals, control signals, and address signals, between the centralprocessor and a system controller 34 (typically called a “Northbridge”).The system controller provides a bridging function between the one ormore central processors 120, a graphics subsystem 126, the memorysubsystem 112, and a PCI (Peripheral Controller Interface) bus 128. ThePCI bus 128 is controlled by a Peripheral Bus Controller 130. ThePeripheral Bus Controller 130 (typically called a “Southbridge”) is anintegrated circuit that serves as an input/output hub for variousperipheral ports. These peripheral ports could include, for example, akeyboard port 132, a mouse port 134, a serial port 136 and/or a parallelport 138 for a video display unit, one or more external device ports140, and networking ports 142 (such as SCSI or Ethernet). The PeripheralBus Controller 130 could also include an audio subsystem 144.

The processor 120 is typically a microprocessor. Advanced Micro Devices,Inc., for example, manufactures a full line of ATHLON™ microprocessors(ATHLON™ is a trademark of Advanced Micro Devices, Inc., One AMD Place,P.O. Box 3453, Sunnyvale, Calif. 94088-3453, 408.732.2400,800.5128.8450, www.amd.com). The Intel Corporation also manufactures afamily of X86 and P86 microprocessors (Intel Corporation, 2200 MissionCollege Blvd., Santa Clara, Calif. 95052-8119, 408.765.8080,www.intel.com). Other manufacturers also offer microprocessors. Suchother manufacturers include Motorola, Inc. (1303 East Algonquin Road,P.O. Box A3309 Schaumburg, Ill. 60196, www.Motorola.com), InternationalBusiness Machines Corp. (New Orchard Road, Armonk, N.Y. 10504, (914)499-1900, www.ibm.com), and Transmeta Corp. (3940 Freedom Circle, SantaClara, Calif. 95054, www.transmeta.com).

The preferred operating system is WINDOWS® (WINDOWS® is a registeredtrademark of Microsoft Corporation, One Microsoft Way, Redmond Wash.98052-6399, 425.882.8080, www.Microsoft.com). Other operating systems,however, are also suitable. Such other operating systems would includethe UNIX® operating system (UNIX® is a registered trademark of the OpenSource Croup, www.opensource.org), the UNIX-based Linux operatingsystem, WINDOWS NT®, and Mac® OS (Mac® is a registered trademark ofApple Computer, Inc., 1 Infinite Loop, Cupertino, Calif. 95014,408.996.1010, www.apple.com).

The system memory device (shown as memory subsystem 112, flash memory114, or peripheral storage device 116) may also contain an applicationprogram. The application program cooperates with the operating systemand with a video display unit (via the serial port 136 and/or theparallel port 138) to provide a GUI for the NBIS Management Module 110,The GUI typically includes a combination of signals communicated alongthe keyboard port 132 and the mouse port 134. The GUI provides aconvenient visual and/or audible interface with the customer or user ofthe computer system 100. As is apparent to those of ordinary skill inthe art, the selection and arrangement of the NBIS Management Module 110to manage NBIS Management Services may be programmed over a variety ofalternate mediums, such as, for example, a voice-activated menu prompt,an interactive session with an telecommunications network administrator,and the like.

The NBIS Management Module 110 allows a user to manage NBIS ManagementServices, such as: (1) allowing the user to customize rules and usergroups associated with a rule-based engine of the rule-based dataserverincluding an access agent, a security agent, a messaging agent, atransaction agent, and a troubleshooting agent; (2) allowing the user tocustomize presentation, features, and/or management of an incomingelectronic message (e.g., an email, an attached object, a compatibleobject, a transaction reply, a transaction notification, and/or otherelectronic communications); and (3) allowing the user to control thetelecommunications network and/or a data network connection with his/herlegacy system. For example, the user may select an Access Agent having auser group list to add, delete, or modify participant information, suchas, associated service node addresses, IP addresses, email addresses,and/or other electronic address information associated with each NBISparticipant. An address of the user group list is associated with anincoming electronic message (shown as reference numeral 240 in FIG. 2)and acts as a trigger (similar to decoding an ICLID signal fortelecommunication special service features offered by telecommunicationservice providers) to send the electronic message to a NBIS rule-basedapplication dataserver (shown as reference numeral 258 in FIG. 2). TheNBIS Management Module 110 also allows the user to customize features,such as electronic message handling options. For example, the NBISManagement Module may split a user's screen into two viewing areas andpresent the incoming electronic message in one portion and presentinformation associated with an attached object and/or a compatibleobject that has been or that might be integrated into the user's legacysystem. Further, the NBIS Management Services may allow the user tocontrol whether to accept, decline, or postpone integration of thecompatible object into the user's legacy system or might be set toautomatically accept, decline, or postpone integration depending on asending participant's address. Finally, the NBIS Management Module 110of the computer system may provide the IP address or the like so thatthe telecommunications network and/or the data network can communicatethe electronic message, and, thus integrate telephony events and datanetwork events with the user's computer system.

FIG. 2 is a schematic showing an exemplary operating environment for atelecommunications network-based information system (NBIS) 200. The NBIS200 includes a shared, interconnected network 210 of one or moreswitches 220 that provide access points of presence for one or morelegacy systems 230. Each legacy system 230 includes at least onecomputer system 100 having the NBIS Management Module 110 (including theIP address or other communications address associated with aparticipant's telecommunications network and/or data network,connection) residing within the computer system 100, atelecommunications network 250 typically including a service switchingpoint (SSP) 252, a sendee control point (SCP) 254, an Intranet 256, anda NBIS Rule-Based Application Dataserver 258, an Internet ServiceProvider (e.g., America On-Line) 260, a data network 262, a gateway 264,an Integrated Delivery System (IDS) 270, and external data sources 280.Each switch 220 allows the connected legacy systems 230 to communicateelectronic messages 240 via the telecommunications network facility 250,such as, for example, a central office (CO), a mobile telephoneswitching office (MTSO), and/or a combination CO/MTSO. Thetelecommunications network facility 250 may use any means of couplingone switch 220 to the telecommunications network facility 250, but thecoupling means is preferably high-capacity, high-bandwidth opticaltransport services, Gigabit Ethernet services, and/or the like. As thoseof ordinary skill in the art of telecommunications understand, thetelecommunications network facility 250 could also link each switch 220via other appropriate means, such as, for example a Synchronous OpticalNetwork (SONET) structure with redundant, multiple rings.

Typically, a customer and/or user of the NBIS Management Sendees usesthe computer system 100 to gain access to the NBIS 200. For example, ifa user wishes to send, receive, or access voice, video, and/or data(e.g., read and respond to e-mail, order test results, view video-clipsincluding static images, listen to recorded information, engage in aninteractive-diagnosis session, etc.), then the computer system 100connects with the interconnected network 210 via switch 220. Eachelectronic message 240 sent from a computer system 100 of theparticipant's legacy system 230 is routed through the telecommunicationsnetwork 250 via switch 220. Communications signals associated with theaddress of the electronic message 240 arrive at SSP 252 that analyzesthe signals and determines whether the electronic message 240 isaddressed to another NBIS participant. Depending on the address andcontent of the electronic message (e.g., whether or not the electronicmessage is to a non-participant, whether or not an object is attached,etc.), the SSP 252 may route the electronic message immediately over thetelecommunications network 250 to attempt a connection or the SSP maycommunicate with SCP 254 for further electronic message processing androuting information (including eventual routing to the NBIS Rule-BasedApplication DataServer 258 if the electronic message 240 is to anotherNBIS participant). The NBIS 200 may include wired, optical, and/orwireless elements and may further include private network elements, suchas private branch exchanges (PBXs), and/or other elements (not shown).The telecommunications network 250 includes Advanced Intelligent Network(AIN) componentry controlling many features of the network. Thetelecommunications network 250 or switch 220 could also include apacket-based “soft switch” that uses software control to provide voice,video, and/or data services by dynamically changing its connection datarates and protocols types. If the telecommunications network 250 orswitch 220 should include a Softswitch, the AIN componentry is replacedby an application server that interfaces with the Softswitch via apacket protocol, such as Session Initiation Protocol (SIP). Thesignaling between the computer system 100, the switch 220, thetelecommunications network 250 including AIN componentry, and the datanetwork 262, however, are well understood in by those of ordinary skillthe art and will not be further described. Further, those of ordinaryskill in the art will be able to apply the principles of this inventionto their own legacy systems including their network configurations whichmay differ substantially from the telecommunications system shown in thefigures.

The NBIS Rule-Based Application Dataserver 258 communicates with SCP 254and Intranet 256 to effectively provide NBIS Management Services. TheseNBIS Management Services allow a NBIS participant to control access,sharing, notification, routing, security, transactions, troubleshooting,management, and/or additional processing of electronic messagesexchanged to/from other NBIS participants. For example, NBIS ManagementServices allows a user to control how the object is processed, into thereceiver legacy system including (i) sending the object to a storagedevice associated with the telecommunications service provider, (ii)archiving the object, (iii) encrypting the object, (iv) copying theobject, and (v) associating the object with related electronic data inthe receiver legacy system. Further, the NBIS Management Services may beactivated, de-activated, administered, and/or otherwise managed by theuser or another entity with authorization (e.g., telecommunicationsservice provider). Thus, NBIS Rule-Based Application Dataserver 258functions as a computer server, database, and processor that isdedicated to managing NBIS participant, activity including theircommunication of electronic messages over the interconnected network210. In an embodiment, the NBIS Rule-Based Application Dataserver 258has the ability to communicate with the data network 262 using standardtransmission control protocol and Internet protocol (TCP/IP) or otherappropriate protocols. Further, the NBIS Management Module 110, may bedownloaded from ISP 260, NBIS Rule-Based Application Dataserver 258,Intranet 256, or provided on a storage media (e.g., diskette, CD-ROM, orinstalled by the computer system manufacturer) to a subscribing customeror user to install on the computer system 100 to enable, disable, andfurther control a variety of the NBIS Management Services.

Referring now to FIG. 3, the participant interacts with the NBISManagement Module 110 and with Intranet 256 to access and login to theNBIS Rule-Based Application DataServer 258 and to establish the NBISRule-Based Profile 300. The NBIS Rule-Based Application Dataserver 258stores one or more NBIS Rule-Based Profiles 300 that include data andapplications associated, with an Access Agent 311, a Security Agent 312,a Messaging Agent 313, a Transaction Agent, and a Troubleshooting Agent315. For example, the Access Agent 311, Security Agent 312, MessagingAgent 313, Transaction Agent, and Troubleshooting Agent 315 may containa variety of fields and/or files associated with at least one of thefollowing: login information associated with a participant, passwordentered by the participant, telephone number or Service Node of theparticipant (this may include a plurality of addresses that areassociated with a Service Node or other switch serving the legacysystem), TCP/IP address of the participant, profile of the computersystem 100 or other communications device associated with the incomingelectronic message (e.g., presentation formats for variouscommunications devices), a time or date identifier (e.g., day of week orcalendar date), other information associated with the communicationssignal, size and content of electronic message (including types of filesthat are transmitted, as an attached object), transaction reply(s),transaction notification(s), display of a GUI (e.g., color, font,placement of NBIS Management Module on screen, etc.), NBIS ManagementService defaults (e.g., whether the IDS automatically re-formats theattached object to a compatible object and updates the receiving legacysystem with the compatible object), and other selections related to NBISManagement Services, such as electronic message features, electronicmessage routing, and troubleshooting problems or error messages.

FIG. 4 illustrates an embodiment of establishing a local NBIS Rule-BasedProfile 400 to interact with the NBIS Rule-Based Profile of theinterconnected network 210. The NBIS Management Module 110 of computersystem 100 is used to establish, store, and manage the NBIS Rule-BasedProfile 400 for legacy system (i.e., the hospital's legacy system). Thelegacy system stores one or more NBIS Rule-Based Profiles 400 thatinclude data and applications similar to NBIS Rule-Based Profiles 300.The NBIS Rule-Based Profiles 400 provide increased security by allowingthe participant to internally control electronic information, utilizeexisting databases to add, delete, or otherwise change electronicinformation, control how the participant's legacy system interacts withthe IDS, and control routing instructions within, its legacy system.

FIG. 5 is a schematic showing an exemplary framework for the flow of theelectronic message 240 through the NBIS 200. Typically, the flow of theelectronic message 240 involves the participant using the computersystem 100 to create the electronic message 240 with an attached object(step 500). The participant may create the electronic message 240 usinga variety of software applications including electronic messaging, wordprocessing, and others (e.g., MICROSOFT OUTLOOK® and MICROSOFT WORD® areregistered trademarks of Microsoft Corporation, One Microsoft Way,Redmond Wash. 98052-6399, 425.882.8080, www.Microsoft.com).Alternatively, the electronic message 240 may be created using the NBISManagement Module 110 that includes instructions to/for the IDS 270. Theelectronic message 240 is routed and received in the telecommunicationsnetwork 250 (step 510). In an embodiment, the NBIS Rule-Based DataServer258 determines whether external data sources 280 need to be queried forrelated electronic data or for retrieving an object that is linkedrather than attached to the electronic message. Next, thetelecommunications network 250 interprets the electronic messageincluding the attached object, related healthcare data, and/or thelinked object (step 520) using network elements including the NBISRule-Based Application DataServer 258. Thereafter, the NBIS Rule-BasedApplication. DataServer 258 routes the object (e.g., the attachedobject, related healthcare date, and/or the linked object) to the IDS270 so that the object may be interpreted from the sending participant'slegacy system for compatible exchange with the receiving participant'slegacy system (i.e., from the hospital's legacy system to thephysician's legacy system) (step 530). The IDS 270 may be a stand alonesystem (not shown in the figures), the IDS 270 may be integrated intothe telecommunications network 250 (as shown in FIG. 2), the IDS 270 maybe integrated with one of the participant's legacy systems (not shown inthe figures) that is accessed by the telecommunications network 250 ordata network 262, or the IDS 270 may be a combination of these systems(not shown). No matter how the IDS 270 is deployed, the interpretedobject is received (step 540), processed so that the object iscompatible for the receiving legacy system, (step 550), and associatedwith a transaction reply (e.g., a communication to the receivingparticipant about the electronic message including information about theattached object or the compatible object) or with a transactionnotification (e.g., a communication to the sending participant about theelectronic message including information about the attached object orthe compatible object) (step 560). Thereafter, the transaction replyand/or the transaction notification are routed through thetelecommunications network 250 (step 570) and forwarded to the receivinglegacy system (step 580) or to the sending legacy system (not shown).The NBIS Management Module 110 presents the electronic message 240 sothat the receiving participant of the computer system 100 has immediateaccess, notification, and management of the electronic message 240including the compatible object and updated data in the receiving legacysystem.

FIG. 6 illustrates a telecommunications network-based real estateinformation system 600 similar to the telecommunications systemdisclosed in FIG. 2. As is apparent to one of ordinary skill in the art,the subject-specific group of participants may be tailored to anyindustry of participants that seek to leverage the assets of atelecommunications network in order to more efficiently shareinformation, automate business processes, and further enhance marketposition.

FIGS. 7-8 are schematics showing a variety of wired and wirelesscommunications devices communicating the electronic message 240 throughthe shared, interconnected network 210 according to alternateembodiments of this invention. The means of coupling the computer system100 or other communications device (shown as reference numerals 702-716)to the switch 220 include a variety of means, including opticaltransmission of electronic data, wireless transmission of electronicdata, and/or fixed-wire transmission of electronic data (e.g., via alocal loop of a telecommunications network to communicate electronicdata). Fiber optic technologies, spectrum multiplexing (such as DenseWave Division Multiplexing), Ethernet and Gigabit Ethernet services, andDigital Subscriber Lines (DSL) are just some examples of the couplingmeans.

FIG. 7 illustrates a telecommunications network-based information system700 similar to the telecommunications system disclosed in FIG. 2;however, telecommunications network-based information system 700illustrates an embodiment of the call flow for alternate communicationsdevices. Telecommunications system 700 includes alternate communicationsdevices that include a personal digital assistant (PDA) 702, an IPcellular phone 704, a modem 706, an interactive pager 708, a globalpositioning system transceiver 710, an MP3 player 712, a digital signalprocessor (DSP) 714, and an interactive television 716. These alternatecommunications devices communicate via an antenna 720 communicating withan MTSO 730 that transmits the electronic message 240 to the switch 220.Switch 220 routes the electronic message 240 to the shared,interconnected network 210. In addition, FIG. 7 illustrates that thecomputer systems of the legacy system include a variety ofcommunications devices including personal computer systems 100 andwireless communications devices, such as PDA 702. Alternatively, aremote computer system, such, as personal computer system 100, may alsoconnect to the shared, interconnected network 210 (typically via a modemconnection (not shown)). Regardless of the communications device used tosend the electronic messages 240, the electronic messages 240 may needto be formatted accordingly for the receiving communications device(including audio, text (e.g., ASCII), video, other digital formats, andcombination thereof). Thus, the NBIS Rule-Based Application DataServer258 has the intelligence to associate the presentation capabilities ofthe alternate communications device.

FIG. 8 illustrates a telecommunications network-based information,system 800 similar to the telecommunications system 700 disclosed inFIG. 7; however, telecommunications network-based information system 800includes a communications device gateway 810 connected with a datanetwork 820 and a communications server 830 so that the electronicmessage communicated to/from, switch 220 may be appropriately formattedfor presentation on alternate communications devices 702-716. Forexample, if the alternate communications device uses the WirelessApplication Protocol (WAP) technique, then the electronic message 240 iscommunicated to a communications (“Comm”) server 830. The communicationsserver 830 formats the electronic message 240 into one or more WirelessMark-up Language (WML) messages that are communicated over a datanetwork 820 to a communications device gateway 810. The communicationsdevice gateway 810 then interfaces with the MTSO 830, and the MTSO 830then wirelessly communicates the electronic message to the pager 708 orthe wireless personal data assistant 704 (or a WAP phone). The WirelessMark-up Language (WML) and the WAP technique are known and will not befurther described. This is a description of a solution for a specificwireless protocol, such as WAP. This solution may be clearly extended toother wireless protocol, such as i-mode, VoiceXML (Voice extensibleMarkup Language), Dual Tone Multi-Frequency (DTMF), and other signalingmeans.

FIGS. 9-10 illustrate a flowchart showing an overview of a process ofproviding the telecommunications network-based information systemservice to a customer according to an embodiment of this invention.While the process in FIGS. 9-10 are shown in series, these processes mayoccur in different orders and/or at simultaneous times as one ofordinary skill in the art will understand.

Referring now to FIG. 9, a NBIS participant (e.g., a user) associatedwith a first legacy system transmits an electronic message to a secondNBIS participant associated with a second legacy system (block 900). Atelecommunications network (TN) detects an incoming electronic messagefrom the first NBIS user to the second NBIS user (block 910). Thetelecommunications network decodes the incoming electronic message for(1) an attached object and/or other related electronic data betweenlegacy systems (e.g., queried data from an external data source 280, alinked object, data that is cut and pasted into tire body of an email,etc.), (2) preliminary security verification, and (3) preliminaryauthentication (e.g., data and/or participants may be authenticated)(block 920). Next, the telecommunications network interprets theattached object and/or other related electronic data using a rule-basedapplication server (e.g., NBIS Rule-Based Application DataServer shownas reference numeral 258 in FIG. 2) to categorize and associate rulebased agents, fields, and/or files (block 930), The attached objectand/or other related electronic data is then, processed according to howan Integrated Delivery System (IDS) is configured (e.g., integrated intothe telecommunications network or accessed separate from thetelecommunications network). If the integrated delivery system is notintegrated with the telecommunications network (e.g., the integrateddelivery system is accessed separate from the telecommunicationsnetwork), then the telecommunications network routes the attached objectand/or other related electronic data to the integrated delivery systemassociated with the first and the second legacy systems (block 940), andthe integrated delivery system processes the attached object and/orother related electronic data so that the attached object and/or otherrelated electronic data can be exchanged between legacy systems (block950). If the integrated delivery system is integrated with thetelecommunications network, then the telecommunications networkprocesses the attached object and/or other related electronic data intothe integrated delivery system so that the attached object and/orrelated electronic data can be exchanged between the first and thesecond legacy systems (block 960). By allowing both IDS architects, NBISManagement Services may be dynamically implemented across differentplatforms.

The method then continues with block 1000 of FIG. 10. The rule basedengine determines whether to activate a transaction reply and/or atransaction notification (block 1000). If there is no transaction replyand/or no transaction notification, then the telecommunications networkhandles the electronic message and/or other related electronic dataaccording to instructions from the rule-based engine (block 1010).Alternatively, if a transaction replay and/or transaction notificationis activated, then the telecommunications network selects theappropriate transaction reply and/or transaction notification (block1020), routes the transaction replay and/or transaction notification toa computer system or other communications device (block 1030), and aclient application (e.g., NBIS Management Module 110) residing on thecomputer system or other communications device presents the transactionreply and/or transaction notification (block 1040).

While several exemplary implementations of embodiments of this inventionare described herein, various modifications and alternate embodimentswill occur to those of ordinary skill in the art. Accordingly, thisinvention is intended to include those other variations, modifications,and alternate embodiments that adhere to the spirit and scope of thisinvention.

1. A method, comprising: associating a sender's legacy system and areceiver system to an integrated delivery system that enables anexchange of data; receiving an electronic message from a sender'saddress that is destined for a recipient's address and having anattached object associated with the sender's legacy system; associatingthe sender's address and the recipient's address to a list of healthcare participant addresses; sending the electronic message to arule-based engine that interprets the attached object using a set ofrules when both the sender's address and the recipient's address arematched to the list of health care participant addresses; and when thesender's address and the recipient's address do not match the list ofhealth care participant addresses, then receiving an identifier thatassociates the electronic message with another legacy system and with anon-participant legacy system.
 2. The method according to claim 1,further comprising categorizing the attached object.
 3. The methodaccording to claim 2, further comprising converting the attached objectbased on the category.
 4. The method according to claim 1, furthercomprising converting the attached object from a first legacy dataformat associated with the sender's legacy system to a second legacydata format compatible with a receiver's legacy system.
 5. The methodaccording to claim 4, further comprising automatically accepting theconversion of the attached object based on the sender's address.
 6. Themethod according to claim 1, wherein when the rule-based engine appliesa sender reply rule, then selecting a transaction reply for delivery tothe sender's address.
 7. The method according to claim 1, wherein whenthe rule-based engine applies a receiver notification rule, thenselecting a transaction notification for delivery to the recipient'saddress.
 8. The method according to claim 1, further comprisingassociating the sender's legacy system and the receiver's legacy systemwith an integrated delivery system.
 9. The method according to claim 1,further comprising accessing a profile stored in a database.
 10. Asystem, comprising: a processor executing code stored in memory thatcauses the processor to: associate a sender's legacy system and areceiver system to an integrated delivery system that enables anexchange of data; receive an electronic message from a sender's addressthat is destined for a recipient's address and having an attached objectassociated with the sender's legacy system; associate the sender'saddress and the recipient's address to a list of health care participantaddresses; send the electronic message to a rule-based engine thatinterprets the attached object using a set of rules when both thesender's address and the recipient's address are matched to the list ofhealth care participant addresses; and when the sender's address and therecipient's address do not match the list of health care participantaddresses, then receive an identifier that associates the electronicmessage with another legacy system and with a non-participant legacysystem.
 11. The system according to claim 1, further comprising codethat causes the processor to categorize the attached object.
 12. Thesystem according to claim 11, further comprising code that causes theprocessor to convert the attached object based on the category.
 13. Thesystem according to claim 1, further comprising code that causes theprocessor to convert the attached object from a first legacy data formatassociated with the sender's legacy system to a second legacy dataformat compatible with a receiver's legacy system.
 14. The systemaccording to claim 13, further comprising code that causes the processorto automatically accepting the conversion of the attached object basedon the sender's address.
 15. The system according to claim 1, furthercomprising code that causes the processor to select a transaction replyfor delivery to the sender's address when the rule-based engine appliesa sender reply rule.
 16. The system according to claim 1, furthercomprising code that causes the processor to select a transactionnotification for delivery to the recipient's address when the rule-basedengine applies a receiver notification rule.
 17. The system according toclaim 1, further comprising code that causes the processor to associatethe sender's legacy system and the receiver's legacy system with anintegrated delivery system.
 18. The system according to claim 1, furthercomprising code that causes the processor to access a profile stored ina database.
 19. A memory device storing processor executableinstructions for performing a method, the method comprising: associatinga sender's legacy system and a receiver system to an integrated deliverysystem that enables an exchange of data; receiving an electronic messagefrom a sender's address that is destined for a recipient's address andhaving an attached object associated with the sender's legacy system;associating the sender's address and the recipient's address to a listof health care participant addresses; sending the electronic message toa rule-based engine that interprets the attached object using a set ofrules when both the sender's address and the recipient's address arematched to the list of health care participant addresses; and when thesender's address and the recipient's address do not match the list ofhealth care participant addresses, then receiving an identifier thatassociates the electronic message with another legacy system and with anon-participant legacy system.
 20. The memory device according to claim19, further comprising code for categorizing the attached object.